Gold Medal Software 3

home *** CD-ROM | disk | FTP | other *** search

/ Gold Medal Software 3 / Gold Medal Software - Volume 3 (Gold Medal) (1994).iso / graphics / ctoc41.arj / CTC.DOC < prev next >

Wrap

Text File | 1993-10-01 | 41KB | 842 lines

C O D E T O C O D E _____________________ (C) Copyright 1989, 1990 ALPHABTYES, INCORPORATED 111 Eighth Street, S.E. Washington, D.C. 20003 (202) 546-4119 Bruce Robey CompuServe: 71131,2734 Version 4.1 ┌─────────┐ This program is produced by a ┌─────┴───┐ │ (R) member of the Association of ──│ │o │────────────────── Shareware Professionals (ASP). │ ┌─────┴╨──┐ │ Association of ASP wants to make sure that │ │ │─┘ Shareware the shareware principle works └───│ o │ Professionals for you. If you are unable to ──────│ ║ │──────────────────── resolve a shareware-related └────╨────┘ MEMBER problem with an ASP member by contacting the member directly, ASP may be able to help. The ASP Ombudsman can help you resolve a dispute or problem with an ASP member, but does not provide technical support for members' products. Please write to the ASP Ombudsman at P.O. Box 5786, Bellevue, WA 98006 or send a Compuserve message via CompuServe Mail to ASP Ombudsman 70007,3536 Shareware Concept _________________ CODE TO CODE is Shareware, not in the Public Domain. You are granted, at no charge, the right to determine the suitability of this software for your needs. If you do find CODE TO CODE suitable and make use of it, you are expected to register with the author. Registration will remove the delay screen, grant unlimited telephone support privileges and provide printed documentation with ample screen examples. Your contribution helps Shareware authors bring better and more affordable software to you. Please redistribute this program to others. Registration $29.00 Visa and MasterCard honored DISCLAIMER OF WARRANTY ______________________ DUE TO THE LARGE NUMBER OF HARDWARE AND SOFTWARE ENVIRONMENTS INTO WHICH THIS PROGRAM MAY BE PLACED, NO WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE IS OFFERED. THOROUGHLY TEST THIS PROGRAM WITH NON-CRITICAL DATA BEFORE RELYING ON IT. THE USER MUST ASSUME THE ENTIRE RISK OF USING THIS PROGRAM. THE SELLER'S MAXIMUM LIABILITY WILL BE LIMITED TO REFUND OF THE PURCHASE PRICE OR PROGRAM REPLACEMENT. TABLE OF CONTENTS _________________ Purpose......................................................1 How It Works.................................................1 What It Can't Do.............................................2 Installation Hard Disk................................................3 Floppy Disk..............................................3 Operation Decode.......................................................3 Ventura Publisher........................................4 XyWrite..................................................5 Penta....................................................5 Magna....................................................6 Recode.......................................................6 Split........................................................7 Join.........................................................7 Make.........................................................8 Change.......................................................9 Quads........................................................9 Main Screen Options..........................................9 Command Line Options.........................................11 NOTE: if you are updating from a previous version of CODE TO CODE skip to page 8. ALPHABYTES, INCORPORATED is a member of: The Association of Shareware Professionals Printing Industry of America Printing Industry of Metropolitan Washington National Composition and Prepress Association Code to Code is a trademark of AlphaBytes, Incorporated Ventura Publisher is a trademark of Ventura Software, Inc. XyWrite is a trademark of XyQuest, Inc. Penta is a trademark of Penta Systems International. MagnaType is a trademark of Magna Computer Systems. Page 1 Purpose _______ CODE TO CODE is a collection of programs, written in Microsoft "C", designed to move, delete or translate codes from various DTP, word processor, and typesetter files. CODE TO CODE can: ■ Move codes from an encoded file to a separate uncoded file. The "uncoded" file can be edited without cumbersome and cryptic codes in the way. After edit- ing, the codes can be restored to the "decoded" file, creating a new complete file. ■ Permanently remove (strip) the codes from the file. ■ Quickly build translation tables automatically. ■ Translate codes between most typesetting, word processing and desktop publishing systems. ■ Split large files into smaller files, with user controlled break points. The split files may be edited and then rejoined into one big file. Applications ____________ ■ Automatically create on-line service documents using DTP or typesetter files. ■ Allow editors --intimidated by cryptic codes-- to easily edit code-free documents and then automatically have the codes reinserted. ■ Spell-check or run a thesaurus on a "decoded" file. With the codes removed spell-checkers will not flag the codes as misspelled words. How It Works ____________ CODE TO CODE reads the ASCII file designated as the Encoded file, searching for codes. Codes are defined as characters that occur between two delimiters. The program asks for the delimiters for the type of file to be converted. Examples: Program Delimiters Precedence Ventura Publisher < > @ XyWrite dec. 174,175 « » none Penta [ ] ; Page 2 Magna < > $ When CODE TO CODE encounters the opening delimiter it writes the subsequent characters to the Code file until it reaches the closing delimiter. The code is considered complete after the closing delimiter. The program may optionally place a marker (, ~, *, etc.) in the Uncoded file while continuing to write the next characters, all this time searching for the next opening delimiter. What It Can't Do ________________ ** Once the markers are placed in the code file they cannot be erased or reordered. The markers indicate the exact location where the code is to be returned. The codes are replaced in sequential order. Codes may be freely add or delete copy while editing. However, please be certain not to move a code out of sequence or delete it. ** WordPerfect, WordStart and other word processors that use proprietary file formats must be converted to ASCII before using them with CODE TO CODE. See the word processor manual for ASCII file conversion. ** Penta files can be coded without a closing delimiter. CODE TO CODE can be configured in the setup menu to treat a space or CR/LF (carriage return/linefeed) as a closing delimiter. This will work properly for most codes. However, codes such as [epNow will not be handled properly. If there is enough user response, subsequent versions of CODE TO CODE will handle this situation. See the Penta section of this document for more details. Installation ____________ The self-extracting archive file will unbundle the following files: CTC.EXE This is the main program. It operates as a shell for the other "EXE" programs. Although each of of the programs can be operated independently from the command line, initial use should be limited to CTC.EXE -- the shell program. DECODE.EXE As its name implies, this program locates and removes the codes and creates the Uncoded and Code files. RECODE.EXE This Program reassembles the Code file with the Uncoded file resulting in a new Encoded file. FILE.EXE This program splits and rejoins files. Use the /S switch to split and /J to join the files. Page 3 CTC.DTA This is a very small file that tells CODE TO CODE how to configure CTC with your system. CTC.DOC This is the file that contains this documentation. QUADS.EXE For certain typesetting systems it is necessary to insert carriage returns after quad codes. QUADS.EXE allows the insertion of carriage returns after user specified quad.codes <QL>, <QC>, <EP>, etc. MAKE.EXE This program automatically builds (makes) translation tables for use for use by CHANGE.EXE. CHANGE.EXE This program will automatically search the original codes in the code file and replace them with the specified replacements in a new code file. Hard Disk Installation Copy all of files above to a subdirectory of your choice. The DOS file COMMAND.COM must be in the PATH statement or located in the working sub- directory. Example: MD\CODES CD\CODES COPY A:*.* CTC Floppy Disk Installation Copy all of the files above to a working floppy disk. Please copy the file COMMAND.COM from the DOS disk to the CODE TO CODE subdirectory if COMMAND.COM is not the PATH. Operation _________ To Start The Program At the DOS prompt type CTC followed by ENTER. If you have a monochrome or LCD monitor type CTC /M followed by ENTER. Please note that there is a space before the /M. For unregistered versions of CODE TO CODE a shareware screen will appear for 3 seconds. Registered versions of the program will start immediately. Notice that the main screen appears to be split horizontally in two parts. The top half of the screen refers to decode, split and make functions while the bottom half refers to the recode, join and change functions. To Decode A File The cursor flashes at the first question [D]ecode or [R]ecode the file? Selecting 'D' will display the Setup Menu to insure the system is configured correctly for the type of file to be converted. Most errors are the result of improper values in the Setup Menu. Page 4 After the setup menu the top, or decode, portion of the screen becomes highlighted while the cursor flashes on the question, "What is the name of the Encoded file?" Answer this question with the drive, path and file name of the file that is to be decoded. Example: What is the name of the Encoded file? d:\xywrite\ventura.doc Type the answer followed by ENTER. Your answer will become capitalized indicating the answer is complete. The cursor will then move to the next question, "What is the name of the Code file?" Answer this question with the drive, path, and file name of the file to hold the codes. This file will contain only the codes that have been extracted from the Encoded file. Example: What is the name of the Code file? d:\xywrite\ventura.cds Type the answer followed by ENTER. Your answer will become capitalized indicating the answer is complete. The cursor will then move to the third question, "What is the name of the Uncoded file?" Again, answer this question with the drive, path and file name of the file to hold the decoded text. This file will contain the text without the codes. Markers will have been placed in the positions previously occupied by codes if the program is configured to do so. Example: What is the name of the Uncoded file? d:\xywrite\ventura.ctc IMPORTANT NOTE: If the name for the Code file is omitted, the file is stripped of the codes. No markers are placed in the Uncoded file. To strip a file of codes simply omit the name of the code file. Finally the cursor flashes at the question: What delimits the code? 1) <> 2) {} 3) [] 4) «» 5) other ▒ Answer this question with the number that corresponds to the delimiters used by the file to be converted. Selecting '5' other will allow specification of custom delimiters. Type the number followed by ENTER. CODE TO CODE will now process the file. Ventura Publisher _________________ Ventura Publisher files can originate from a variety of word processors. Unfortunately, some of these programs create files (WordPerfect, WordStar, etc.) that can only be read in their respective program. However, to circumvent this problem, use the FILE TYPE/RENAME option in the EDIT pull down menu to convert the file to ASCII. When the chapter is saved, the file will be saved in an ASCII format suitable for CODE TO CODE. Page 5 Ventura Publisher files contain two coding schemes. Most of the command codes are delimited with the less than < and greater than > characters. Within these delimiters codes will occur that relate to point size, typeface, alignment, etc. One of the most appealing features of Ventura Publisher is the ability to create and use tags to format text. The delimiters used by Ventura tags are the at sign (@) and space(equal sign) space. A typical Ventura tag would appear as follows: @MAINHEAD = @SUBHEAD = @BULLET = To instruct CODE TO CODE to process a Ventura Publisher file, press 'D' for decode. When the setup menu appears,"Space or CR/LF for delimiter?" should be set to 'N'. The precedence character should be the at @ sign. Select a marker character that is compatible with your word processor. and not likely to occur in the text. CODE TO CODE is instructed that every time @ is selected as a delimiter that a Ventura Publisher file is to be processed. Answer 'Y' to the Save these changes?. From the main screen, answer the three file questions appropriately. What delimits the code will be option 1 <>. CODE TO CODE will process the file removing the tags as well as the delimited codes. The new file is now ready to be edited or spell checked in your word processor. XyWrite _______ All versions of XyWrite use the decimal 174 and 175 (French quotes) characters as delimiters. To process a XyWrite file, press 'D' for decode. When the Setup Menu appears, answer 'N' to "Space or CR/LF for delimiter?". Answer 'N' to precedence code. Select a marker character that is compatible with your word processor. Answer 'Y' to "Save these changes?". Answer the next three file questions appropriately. "What delimits the code?" will be option 4.«» CODE TO CODE will process the file. Penta _____ To instruct CODE TO CODE to process a Penta file press 'D' for decode. When the Setup Menu appears, answer 'Y' to "Space or CR/LF for delimiter?" Answer (;) semicolon for the precedence character. These are the Penta autosorts (semicolon followed by a 2-letter mnemonic) CODE TO CODE is instructed that every time (;) is selected as a precedence character, the next two characters will determine a pi character to be called from the pi font. Select a marker character that is compatible with your word processor. Answer 'Y' to "Save these changes?". Answer the three file questions appropriately. "What delimits the code"? will be option 3 []. CODE TO CODE will process the file removing the autosorts as well as the delimited codes. The new file is now ready to be edited with your word processor. Page 6 Magna _____ To instruct CODE TO CODE to process a Magna file, press 'D' for decode. When the Setup Menu appears, answer 'N' to "Space or CR/LF for delimiter?" The precedence character should be the dollar sign ($). These are the Magna dollar sign pi codes (dollar sign ($) followed by a 2-letter mnemonic). CODE TO CODE is instructed that every time $ is selected as a precedence character, that the next two non-numeric characters will determine a pi character to be called from the pi font. Answer 'Y' to the Save to Disk question. Answer the three file questions appropriately. What delimits the code will be option 1 <>. CODE TO CODE will process the file removing the dollar sign pi characters as well as the delimited codes. The new file is now ready to be edited with your word processor. RECODE ______ The recode function is identical for all coding formats. From the main menu type 'R' for recode. The cursor moves to the bottom portion of the screen resting on, "What is the name of the new file?". Answer this question with the drive, path and file name of the file that is to be decoded. Example: What is the name of the new file? d:\xywrite\ventura.ctc Type the answer followed by ENTER. Your answer will become capitalized indicating the answer is complete. The cursor will move to the next question, "What is the name of the Code file?" Answer this question with the drive, path, and file name of the file to hold the codes. This file will contain only the codes that have been extracted from the original file. Example: What is the name of the code file? d:\xywrite\ventura.cds Type the answer followed by ENTER. Your answer will become capitalized indicating that the answer is complete. The cursor will move to the third question. "What is the name of the Coded file?" Again, answer this question with the drive, path and file name of the file to hold the decoded text. It is advisable to make this name different from the original coded file so that the original is not overwritten. CODE TO CODE will, however, beep and display a warning message if you attempt to overwrite the original file. This file contains the text without the codes. Example: What is the name of the new file? d:\xywrite\ventura1.doc Page 7 SPLIT _____ The split function allows the user to split large unmanageable text files into smaller files. The original file can be any length however, the split files are limited to 64K (64000 characters). Just like Decode and Recode above, the split files may be edited and then rejoined to make one large file again. From the main menu type 'S' for split. The cursor moves into the top portion of the screen and rests on the question, "File name of file to be split?". Answer the question with the drive, path and file name of the file that needs to be split. Type the answer followed by ENTER. Your answer becomes capitalized indicating the answer is complete. The cursor will move to the next question, "File name for the split files? (no ext)." Answer this question with the drive, path and file name for the split files. CODE TO CODE will automatically add and increment the extension number starting with 1. Type the answer followed by ENTER. Your answer again becomes capitalized indicating completion. The cursor moves to the question, "String to break the file after?" Answer this question with the string of characters which determines where the file is to be closed and the next one opened. Note: If you are using the command line option this string must be surrounded with quotes. example "[ep]." Typically, typesetter files use the end of paragraph code (<EP> [ep]) while Ventura Publisher uses a carriage return. If this question is left blank, CODE TO CODE will break the file at the first carriage return encountered after reading the number of characters you indicated as the size of the split files. Type the answer followed by ENTER. The answer WILL NOT become capitalized because this string needs to be cap sensitive. The last question is "No. of characters for the split?". Enter any number up to 64000 (no commas). CODE TO CODE reads this number of characters, stops, then continues to read more characters until the break string is encountered. Then the program closes the current file and opens the next. JOIN ____ The join function reassembles the split files into a single file. Select 'J' for join from the main menu. The lower portion of the screen becomes highlighted and the cursor rests on the question, "File name to hold split files?". Answer this question with the drive, path and name of the one large file that will be made up from the smaller split files. Type the answer followed by ENTER. Your answer becomes capitalized indicating the answer is complete. The cursor will move to the next question, "File name of the split files?". Answer this question with the file name (without the extension) of the files that were previously created by the Split option. Answer the question followed by ENTER. Your answer again is capitalized indicating completion. The cursor moves to the final question, "How many split files?". Answer the question with the number of files that the split option previously created. Page 8 MAKE ____ The MAKE function automatically creates a translation tables for use by the CHANGE function. Select 'M' from the main menu. The upper portion of the screen becomes highlighted and the cursor rests on the question," File name of the Code File? Answer this question with the file named used previously with the Decode option. This is the name of the file that contains codes only. Answer the question followed by ENTER. The cursor moves to the final question, "File name for the code table file? (.tbl)". Answer the question with the name of a file to contain the SEARCH/REPLACE couplets. The structure of this file is nothing more than the search code on line one followed by a carriage return and the replacement code on the next line followed by a carriage return. Answer the question followed by ENTER. The program will search the code file looking for distinct codes. A banner will appear at the bottom of the screen indicating the number of distinct codes found. After pressing a key, the first code will be displayed with a prompt for a replacement code. If you wish to replace the code type the replacement followed by ENTER. If you wish to delete the code press ENTER alone. Go through all of the codes typing replacements for the ones you know are appropriate and ENTER by itself for the codes that are not compatible. The MAKE function can handle codes up to 256 characters in length, however, only the first 25 characters are considered significant. Therefore, <this is a test code from would be identical to <this is a test code from a Ventura file>. If the code file contains codes longer than 25 characters and they may be worded similarly, use the manual table creation methods discussed below. ** Translation tables may be created manually using DOS, or any editor or word processor capable of storing a file in an ASCII format. Type the code as it appeared in the file on the first line followed by a carriage return. Then type its replacement on the second line followed by a carriage return. Using this method, it is possible to translate all of the codes from one system to the corresponding codes of another system. Example MagnaType to Ventura Publisher using an ASCII editor [UG1] @HEADLINE = [UG2] @SUBHEAD = $BU <195> Example MagnaType to Ventura Publisher using DOS At the DOS prompt type: copy con mytrans.tbl --copy console and the filename-- [UG1] @HEADLINE = [UG2] @SUBHEAD = $BU <195> ^z --Control Z ENTER Page 9 CHANGE ______ The change function translates the codes by processing the information in the code table file (.tbl) and the code file. Select 'C' from the Main Menu. The lower portion of the screen becomes highlighted and the cursor rests on the question, "File name of the table file (.tbl). Answer the question with the name of the table file you created using the Make function. Press ENTER then the cursor moves to the second question, "What is the name of the old code file?" Answer the question with the name of the file you used when you used the Decode function. Press ENTER and the cursor moves to the final question, "File name of the new code file?". Answer this question with the name of a file to hold the new translated codes. Press ENTER and the program will process the codes. To place the new codes back in the file use the Recode function with the uncoded file, this new code file, and the name of the new finished file. QUADS _____ Many professional typesetting systems automatically filter out carriage returns and multiple spaces. In these cases running DECODE on this type of file will result in a "decoded" file that is ONE HUGE PARAGRAPH. To prevent this, run the QUADS.EXE program before running DECODE. QUADS will allow you to specify two quad codes ([QL],[EP], etc.) that will be converted to a carriage return/line space. Since this problem only affects some users, QUADS.EXE only operates from the command line. The syntax for operating QUADS.EXE is: QUAD [origfile] [newfile] ["1st quad code"] ["2nd quad code"] Example: Quad original.fil fixed.fil "<EP>" "<QL>" Note: The quad codes must be surrounded by quotes. Some command delimiters are interpreted by DOS as redirection operators unless they are set off by quotes. DOS will return a file not found error if the quad code appears without the quotes. Main Screen Options ___________________ F1 ON-LINE HELP On-line help is available in CODE TO CODE by pressing the F1 key almost anywhere in the program. The program documentation can be read while operating the program by using the F4 VIEW option and enter CTC.DOC as the file to view. F2 SETUP Configuration information for the program. F3 DOS Pressing F3 anywhere in the program will suspend CODE TO CODE and return to the DOS prompt. CODE TO CODE is still in memory and can be recalled by typing EXIT at the DOS prompt. You will return to where you were when you left the program. This feature is handy Page 10 for formatting diskettes or viewing a directory. Note: CODE TO CODE must be able to find COMMAND.COM in the working sub directory or in the PATH statement for this option to work correctly. F4 VIEW Pressing F4 will prompt the user for the file name to view. Answer with the file name then press [ENTER]. The file will be displayed one page at a time. Use PGDN to move down a page and use PGUP to backup a page at a time. Use HOME to return to the beginning of the file. CODE TO CODE will default to display tab characters as and carriage returns as <-. F3 will toggle these characters off and on. ESC returns to the CODE TO CODE main menu. F5 CALC F5 offers a full function calculator. The calculator features standard math operations such as ADDITION, SUBTRACTION, MULTIPLICATION, DIVISION and GRAPHIC conversions of Picas & Points to inches and vice versa. At the cursor type the first number of your calculation followed by ENTER. Next type the math operator (* multiply, / divide, + add, - subtract). The cursor will jump to the third shaded box. Type the last number of your calculation followed by ENTER. The answer is displayed to the right. Press ENTER to start another calculation or ESC to return to the main menu. example: 2▒▒▒▒▒▒▒ + 2▒▒▒▒▒▒▒▒ = 4.00 To convert from picas and point to inches, enter the number to be converted followed by ENTER, then type P. The conversion is shown to the right. To convert from inches to picas and points, enter the number to be converted followed by ENTER. Next type I followed by ENTER. The conversion is shown to the right. example: 21,06▒▒▒ Picas & Points -> 3.57 Inches example: 3.57▒▒▒▒ Inches -> 21 picas 6 points *please note: inches are decimal. For example, one and one half inches is notated as 1.50 Picas and points are notated with a coma. For example one and one half Picas is notated as 1,06. Remember Picas and Points are measuring systems with a base of 12 not 10 as in decimal. F10 EXIT Leave the program and return to DOS. Page 11 Advanced Information Command Line Options ____________________ The programs DECODE.EXE, RECODE.EXE, and FILE.EXE are stand alone programs that can operate independently from the command line. Since using these programs from the command line circumvents the CTC.EXE program, certain information has to be passed to each program on the command line. The command line parameters are: NOTE: When using the command line option, the delimiters must be enclosed by quotation marks,("<>" "[]") and you are responsible for checking the contents of the CTC.DTA file. In other words make sure that the three Set Up questions are appropriate for the files you are about to convert. RECODE, DECODE and FILE use the CTC.DTA file. DECODE [delimit] [Encoded file] [Uncoded file] [code file] ───┬── ───┬──── ───────┬──── ────┬─────── ┬──────── │ │ │ │ │ └───────┼─────────────┼─────> Program name │ │ │ │ │ └─────────────┼───────────┼> Delimiters: These must │ │ be placed in quotation │ │ marks example: "<>" │ │ │ └───────────┼─────> Drive, path and file │ name of the file to be │ decoded │ │ └──────────┼─> Drive, path and file │ name of the new file │ to hold the decoded │ text │ └─> Drive, path and file name of the file to hold the codes. RECODE [text file] [code file] [output file] ───┬── ─────┬─── ────┬──── ────┬────── │ │ │ │ └─────────┼──────────┼──────> Program name │ │ │ └──────────┼───────────┼─> Drive path and file │ │ name of the file that │ │ contains the codes │ │ └───────────┼─────> Drive, path and file │ name of the file in │ which to write the │ codes. │ └────────> Drive, path and file name of the file to put the reassembled text and codes in. Page 12 FILE /S [original] [split file] [no. characters] ["break string"] ──┬─ ─┬ ────┬─── ────┬───── ───┬────────── ───┬──────── │ │ │ │ │ │ └───┼──────┼──────────┼────> Program name │ │ │ │ │ │ │ └──────────┼────────> Drive path and file │ │ name of the large file Split │ to be split. │ Switch │ │ │ └───────────┼> Drive, path and file │ name of the file to │ write the split files to. │ │ │ │ └──> Number of characters that each split file should contain. │ String to break each split file on. This string must be surrounded with quotes FILE /J [text file] [split files] [no. of split files] ─┬─ ┬─ ────┬──── ───┬─────── ─┬──────────────── │ │ │ │ │ └───┼───────┼──────────┼────────> Program name │ │ │ │ │ └──────────┼───────────┼─> Drive path and file │ │ │ name of the file that │ │ │ will contain the split files Join │ │ Switch └───────────┼─────> Drive, path and file │ name of the split files │ └─────────> Number of split files that are to be combined MAKE [code file] [table file (.tbl) ──┬─ ─────┬─── ────┬──── ────┬────── │ │ │ │ └───────┼──────────┼──────> Program name │ │ │ └──────────┼───────────┼─> Drive path and file │ │ name of the file that │ │ contains the codes │ │ └───────────┴─────> Drive, path and file name of the file to contain the translation couplets. (SEARCH/REPLACE) Page 13 CHANGE [.tbl file] [code file] [new code file] ───┬── ─────┬─── ────┬──── ────┬────── │ │ │ │ └─────────┼──────────┼──────> Program name │ │ │ └──────────┼───────────┼─> Drive path and file │ │ name of the file that │ │ contains the codes table │ │ └───────────┼─────> Drive, path and file │ name of the file where │ the codes were stored using │ DECODE. │ └────────> Drive, path and file name of the file to put the translated codes in. QUADS [origfile] [newfile] [\"1st quad code\"] [\"2nd quad code\"] ____ _________ _________ _________________ _________________ │ │ │ │ │ └ Program name │ │ │ │ │ │ │ └ Name of the file to process │ │ │ │ └ Name of the new files │ │ │ │ │ └ 1st quad code in quotes ex. \"<EP>\" │ │ │ └ 2nd quad code in quotes.